Use correct error message for duplicate error key in product import#15980
Merged
magento-engcom-team merged 2 commits intomagento:2.3-developfrom Jun 21, 2018
denteblu:url-key-error-message
Merged
Use correct error message for duplicate error key in product import#15980magento-engcom-team merged 2 commits intomagento:2.3-developfrom denteblu:url-key-error-message
magento-engcom-team merged 2 commits intomagento:2.3-developfrom
denteblu:url-key-error-message
Conversation
Contributor
|
|
magento-engcom-team
added
Partner: MageSpecialist
partners-contribution
Contributor
Contributor
|
Hi @denteblu. Thank you for your contribution. |
This was referenced Jun 25, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
During product CSV import, when a Url key duplicate is detected after the validation phase, the error message display only the error template but not the actual error details.
I have changed the
addRowError()call using the detailed error message.Fixed Issues (if relevant)
Manual testing scenarios
Contribution checklist